home *** CD-ROM | disk | FTP | other *** search
- This set of programs provides an (updated) ST port for FSF system of
- documentation called `Texinfo'. Documents prepared in this system can
- be either typeset in a book form (with TeX, but also with troff), or
- displayed on-line with hypertext capabilities on character based
- terminals.
-
- The following programs are included:
- - makeinfo.ttp a formatter with an output in .info format,
- which is accepted by info.ttp viewer
- - info.ttp hypertext viewer for .info files
- - texindex.ttp index formatter for Texinfo files printed with TeX
- - texi2roff.ttp converter into [tn]roff format for Texinfo files
- - texi2index Bourne shell script for making indices for troff.
-
- Programs `makeinfo' and `texindex' come from the current (3.1) Texinfo
- distribution. Unfortunately `info' from the same set, although
- provides many new capabilities, is considered "beta". This really
- means that it is so far quite buggy and has obvious "memory stomping"
- problems. Therefore info.ttp was compiled from modified and fixed
- texinfo-2.16 sources. `texi2roff' is originally distributed
- separately and texi2roff-2.0 served as a basis for this port.
-
- Original complete sources are on a bigger side and contain, among
- other things, over .5 Meg of documentation and other goodies. If you
- are seriously interested in Texinfo you should consider retrieving
- them from usual archives which carry GNU software. prep.ai.mit.edu is
- one of location. Modified ST sources for C programs only are also
- posted to comp.sources.atari.st and to an archive at
- atari.archive.umich.edu (and its mirrors).
-
- Together with a distribution are included sample Texinfo files
- info.txi, makeinfo.txi and, courtesy of Frank Ridderbusch, gcc-st.txi.
- If you never tried info before start simply running makeinfo.ttp and
- giving it as an argument these files - one at at time. Then, without
- changing directory, type 'info', and once info will start follow on
- screen instructions. Sample `dir' file has all neccessary entries.
- You may add to it your own files later following pretty obvious
- format. All these files (dir and .inf) later can be put in any
- directory listed in INFOPATH. This environment variable has a
- compiled in default value of `.,c:\gnu\info' but you may set it
- explicitely to whatever you want. Slash and backslash as path elements
- separators are treated in an equivalent manner. Other usual ST
- conventions for path specifications are also recognized. Try also
- running makeinfo giving it options of `--no-split --no-headers' and
- scrutinize results.
-
- Files produces by makeinfo on ST and on a Unix machine are
- interchangable with an exception of "external" names, which had to be
- squeezed on ST into an 8+3 scheme. Internally they are the same.
- Also info.ttp will not distinguish between info files with CR/LF line
- terminators, or only LF. On Unix side you will have to remove
- superfluous carriage returns. This means that you can "borrow" ready
- info files from your nearest Unix machine (modifying names in an
- obvious, upon examination, way). On the other hand, I successfully
- formatted on Mega with 2.5 Megs of memory the full 550 K of an
- original Texinfo manual (this required separate run with
- `--only-split' to divide into parts a monolitic .inf file from the
- first run).
-
- Enjoy,
- Michal Jaegermann
- ntomczak@vm.ucs.ualberta.ca
- michal@gortel.phys.ualberta.ca
-
- Note about findfile():
- info and makeinfo, as provided, use a modified findfile() function
- which is using comma and colon for path separators, but a colon which
- follow a single letter opening path element and followed by a slash or
- backslash is taken literally. That means that in these executables
- path specifications like
- c:/tmp:c:/lib/info
- c:\tmp,c:\lib\info
- /dev/c/tmp:/dev/c/lib/info
- are all equivalent. If you really want to specify in your path
- subdirectory 'c' of your current directory and which is followed by
- other path entries (not likely, but maybe) use then './c' or '.\c' as
- its name. Otherwise confusion will follow. If for some reasons
- you are unhappy with this convention you will have to recompile.
-